home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
digests
/
digital
/
940071.txt
< prev
next >
Wrap
Internet Message Format
|
1994-11-13
|
24KB
Date: Wed, 16 Mar 94 04:30:41 PST
From: Ham-Digital Mailing List and Newsgroup <ham-digital@ucsd.edu>
Errors-To: Ham-Digital-Errors@UCSD.Edu
Reply-To: Ham-Digital@UCSD.Edu
Precedence: Bulk
Subject: Ham-Digital Digest V94 #71
To: Ham-Digital
Ham-Digital Digest Wed, 16 Mar 94 Volume 94 : Issue 71
Today's Topics:
9k6 baud TheNet X-1J parameters? (2 msgs)
<None>
Baycom Software
BITPK AND TFPCX (Baycom + TPK)
Diesel or Taurus fr HF/VHF mobile??
Guide to the Personal Radio Newsgroups
Looking for information about Path Calculation
New GPS newsgroup
W9GR port to TI DSK - UPDATE
Send Replies or notes for publication to: <Ham-Digital@UCSD.Edu>
Send subscription requests to: <Ham-Digital-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Ham-Digital Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Tue, 15 Mar 1994 21:08:03 GMT
From: ihnp4.ucsd.edu!dog.ee.lbl.gov!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!news.cts.eiu.edu!csjdr1@network.ucsd.edu
Subject: 9k6 baud TheNet X-1J parameters?
To: ham-digital@ucsd.edu
A group of us just got on 9600bps using Tekk radios and a variety of tncs
and modems. On a good clear channel we are using mtu 1024, mss 984 and
window of 1986. We have been fairly successful but don't have that much
experience yet.
Dave KD9AC
------------------------------
Date: Tue, 15 Mar 1994 19:05:52 GMT
From: pacbell.com!well!nbn!sgiblab!sdd.hp.com!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!dog.ee.lbl.gov!newshub.nosc.mil!avalon.chinalake.navy.mil!gawain.nwc.navy.mil!@@ihnp4.ucsd.edu
Subject: 9k6 baud TheNet X-1J parameters?
To: ham-digital@ucsd.edu
Hello all!
I'm putting up a 9k6 baud TheNet node soon, and I'd like any
suggestions as to the timing parameters that it should have.
I know they should be different than 1200 baud, but I don't
really have much experience with 9k6...
Another thing -- TheNet X-1J allows the use of MTU's larger
than 255. Is this an advantage to TCP/IP users, and in
particular 9k6 baud use, where the increased packet sizes
could increase thruput?
Many thanks in advance,
jan
kc6uth
jan@archimedes.chinalake.navy.mil
------------------------------
Date: 15 Mar 94 16:13:35 -0700
From: ihnp4.ucsd.edu!library.ucla.edu!europa.eng.gtefsd.com!howland.reston.ans.net!math.ohio-state.edu!cyber2.cyberstore.ca!nntp.cs.ubc.ca!mala.bc.ca!wagner@network.ucsd.edu
Subject: <None>
To: ham-digital@ucsd.edu
Looking for a FTP site with BITPK.EXE and TFPCX. This is supposedly a copy of
TPK configured for the Baycom modem. TFPCX is the driver.
I have TPK up and running with a Baycom, but am still having mucho trouble with
what is suspect is a problem with BPQZX25. Am also running with an old non-
turbo IBM PC. This could be adding to my frustration.
The main reason for all this is I want YAPP protocol on the Baycom. I hear the
Baycom group is working on this but I am anxious to download a few files and
they are only accessible on YAPP.
--
____________ ____________ ____ _____
/_____ ____/ / _______ / / \ ,' /
/ / / / / / / /\ \ ,' ,'/ /
/ / / / / / / / \ \,' ,' / /
/ / / / / / / / \ ,' / /
/ / / /______/ / / / \,' / /
/__/ /___________/ /__/ /_/
_____________________________________________________
/____________________________________________________/
Proud owner of a dog, cat, bird, old Tractor and a British
Car "If Lucas Electric made guns wars wouldn't start"
------------------------------
Date: 15 Mar 94 12:46:01 -0700
From: ihnp4.ucsd.edu!dog.ee.lbl.gov!agate!howland.reston.ans.net!math.ohio-state.edu!cyber2.cyberstore.ca!nntp.cs.ubc.ca!mala.bc.ca!wagner@network.ucsd.edu
Subject: Baycom Software
To: ham-digital@ucsd.edu
In article <CMo2Bs.4AH@meteor.sbi.com>, mikeq@sbi.com (Michael Queally) writes:
> ---
> Hello folks,
> Does anyone know where I can get information
> on the L2 program used by Baycom. This is the TSR program that
> is used to interface the Baycom terminal program with the hardware modem.
> I am interested in cpu registers etc. that are used to communicate with
> this L2 driver. Any info/sources would be appreciated.
>
> --------------------------------------------------------------
> Mike Queally | Email : mikeq@pivot-sts.sbi.com
>
Don't know about the L2 program, but I have the Baycom system (v1.5) and I
also use TPK (that is another horror story). You might chech about BPQAX25
which is the tsr driver for TPK. I havn't seen any details, but I have been
told the code is out there somewhere. Checking that could give you a leg up.
--
____________ ____________ ____ _____
/_____ ____/ / _______ / / \ ,' /
/ / / / / / / /\ \ ,' ,'/ /
/ / / / / / / / \ \,' ,' / /
/ / / / / / / / \ ,' / /
/ / / /______/ / / / \,' / /
/__/ /___________/ /__/ /_/
_____________________________________________________
/____________________________________________________/
Proud owner of a dog, cat, bird, old Tractor and a British
Car "If Lucas Electric made guns wars wouldn't start"
------------------------------
Date: 15 Mar 94 16:16:15 -0700
From: ihnp4.ucsd.edu!library.ucla.edu!europa.eng.gtefsd.com!howland.reston.ans.net!math.ohio-state.edu!cyber2.cyberstore.ca!nntp.cs.ubc.ca!mala.bc.ca!wagner@network.ucsd.edu
Subject: BITPK AND TFPCX (Baycom + TPK)
To: ham-digital@ucsd.edu
Well I blew that un. Need info on BITPK. Please read my prev posting where I
nulled out the subject...
--
____________ ____________ ____ _____
/_____ ____/ / _______ / / \ ,' /
/ / / / / / / /\ \ ,' ,'/ /
/ / / / / / / / \ \,' ,' / /
/ / / / / / / / \ ,' / /
/ / / /______/ / / / \,' / /
/__/ /___________/ /__/ /_/
_____________________________________________________
/____________________________________________________/
Proud owner of a dog, cat, bird, old Tractor and a British
Car "If Lucas Electric made guns wars wouldn't start"
------------------------------
Date: Tue, 15 Mar 1994 09:25:11 GMT
From: ihnp4.ucsd.edu!sdd.hp.com!apollo.hp.com!hpwin052!hpqmoea!dstock@network.ucsd.edu
Subject: Diesel or Taurus fr HF/VHF mobile??
To: ham-digital@ucsd.edu
Gary Coffman (gary@ke4zv.atl.ga.us) wrote:
: This was a *real* mechanical injection diesel engine. With *all* electrical
: systems disconnected, it still made the pseudo-ignition noise. The best
: guess we could come up with was that the plasma formed by combustion was
: somehow shock exciting something and causing it to radiate. We considered
: static discharges due to the rotating machinery, but we bonded *everything*,
: including finger stock on the crank and cam, and on the injection pump
: cam, and we put anti-static brushes on the clutch, all without making it
: go away. So I don't think that was it. It would sit there at idle in the
: shop and tear up every radio in the place with absolutely *no* electrical
: equipment operating on the vehicle. A real puzzle.
: Gary
A first class enigma ! Ever try a spectrum analyser and
close-field probe on it ? Another thing would have been to try to use a
scope to verify that it was repetitive at engine revs, and if so what it
coincided with. I hate to have missed such a puzzle.
Seems I got a couple of (mild) flames about saying no computers on my
Diesel, well MINE HAS NONE. There's one in the pull-out entertainment
radio, but that just pulls out. No engine management CPU, no computer
aided instruments of airconditioning, manual gears. Nice ! and it meets
all the emissions regulations scheduled to come in up to the end of the
century. It's a direct injection unit, and apart from start-up runs
without any visible smoke even on throttle opening and full boost.
Fuel consumption is better than HALF that of the petrol (gasolene)
version of the same vehicle.. this translates into less CO2 as well as
less money. Direct injection turbodiesels have reduced the particle
problem somewhat, and it looks like the cyclone particle traps should
kill the problem completely. I'm not sure how the petrol engine could
compete afterwards without a CO2 remover....
Cheers
David GM4ZNX
------------------------------
Date: Tue, 15 Mar 1994 12:01:57 GMT
From: ihnp4.ucsd.edu!agate!howland.reston.ans.net!wupost!crcnis1.unl.edu!news.unomaha.edu!news@network.ucsd.edu
Subject: Guide to the Personal Radio Newsgroups
To: ham-digital@ucsd.edu
Posted-By: auto-faq 3.2.1.2
Archive-name: radio/personal-intro
Revision: 1.5 12/18/93 14:15:53
Changes: new mailing lists, .packet rmgroup, and .policy updates
(Note: The following is reprinted with the permission of the author.)
This message describes the rec.radio.amateur.*, rec.radio.cb, rec.radio.info,
and rec.radio.swap newsgroups. It is intended to serve as a guide for the new
reader on what to find where. Questions and comments may be directed to the
author, Jay Maynard, K5ZC, by Internet electronic mail at
jmaynard@oac.hsc.uth.tmc.edu. This message was last changed on 18 September
1993 to add the mailing lists for the new rec.radio.amateur newsgroups, to
note the rmgroup of rec.radio.amateur.packet, and to officially retire some
(in)famous threads of discussion on rec.radio.amateur.policy.
History
=======
Way back when, before there was a Usenet, the Internet hosted a mailing list
for hams, called (appropriately enough) INFO-HAMS. Ham radio discussions
were held on the mailing list, and sent to the mailboxes of those who had
signed up for it. When the Usenet software was created, and net news as we
now know it was developed, a newsgroup was created for hams: net.ham-radio.
The mailing list and the newsgroup were gatewayed together, eventually.
As the net grew, and as packet radio came into vogue, packet discussion began
to dominate other topics in the group and on the list. This resulted in the
logical solution: a group was created to hold the packet discussion, and
another corresponding mailing list was created as well: net.ham-radio.packet
and PACKET-RADIO, respectively.
These two groups served for several years, and went through Usenet's Great
Renaming essentially unchanged, moving from net.ham-radio[.packet] to
rec.ham-radio[.packet]. Readership and volume grew with the rest of the
network.
The INFO-HAMS mailing list was originally run from a US Army computer at
White Sands Missile Range, SIMTEL20. There were few problems with this
arrangement, but one was that the system was not supposed to be used for
commercial purposes. Since one of hams' favorite pastimes is swapping
gear, it was natural for hams to post messages about equipment for sale
to INFO-HAMS/rec.ham-radio. This ran afoul of SIMTEL20's no-commercial-use
restriction, and after some argument, a group was created specifically
for messages like that: rec.ham-radio.swap. This group wasn't gatewayed to
a mailing list, thus avoiding problems.
While all this was happening, other folks wanted to discuss other aspects
of the world of radio than the personal communications services. Those
folks created the rec.radio.shortwave and rec.radio.noncomm newsgroups,
and established the precedent of the rec.radio.* hierarchy, which in turn
reflected Usenet's overall trend toward a hierarchical name structure.
The debate between proponents of a no-code ham radio license and its opponents
grew fierce and voluminous in late 1989 and 1990. Eventually, both sides grew
weary of the debate, and those who had not been involved even more so. A
proposal for a newsgroup dedicated to licensing issues failed. A later
proposal was made for a group that would cover the many recurring legal issues
discussions. During discussion of the latter proposal, it became clear that it
would be desirable to fit the ham radio groups under the rec.radio.*
hierarchy. A full-blown reorganization was passed by Usenet voters in January
1991, leading to the overall structure we now use.
After the reorganization, more and more regular information postings began to
appear, and were spread out across the various groups in rec.radio.*. Taking
the successful example of the news.answers group, where informational postings
from across the net are sent, the group rec.radio.info was created in
December, 1992, with Mark Salyzyn, VE6MGS, initially serving as moderator.
In January, 1993, many users started complaining about the volume in
rec.radio.amateur.misc. This led to a discussion about a second
reorganization, which sparked the creation of a mailing list by Ian Kluft,
KD6EUI. This list, which was eventually joined by many of the most prolific
posters to the ham radio groups, came up with a proposal to add 11 groups to
the rec.radio.amateur hierarchy in April 1993. The subsequent vote, held in
May and early June, approved the creation of five groups:
rec.radio.amateur.digital.misc (to replace .packet), .equipment, .homebrew,
.antenna, and .space.
The Current Groups
==================
I can hear you asking, "OK, so this is all neat history, but what does it
have to do with me now?" The answer is that the history of each group has
a direct bearing on what the group is used for, and what's considered
appropriate where.
The easy one is rec.radio.amateur.misc. It is what rec.ham-radio was renamed
to during the reorganization. Any message that's not more appropriate in one
of the other groups belongs here, from contesting to DX to ragchewing on VHF
to information on becoming a ham.
The group rec.radio.amateur.digital.misc is for discussions related to
(surprise!) digital amateur radio. This doesn't have to be the common
two-meter AX.25 variety of packet radio, either; some of the most
knowledgeable folks in radio digital communications can be found here, and
anything in the general area is welcome. The name was changed to emphasize
this, and to encourage discussion not only of other text-based digital modes,
such as AMTOR, RTTY, and Clover, but things like digital voice and video as
well. The former group, rec.radio.amateur.packet, should be removed by
September 21st, 1993. It is obsolete, and you should use .digital.misc
instead (or the appropriate new mailing list, mentioned below). The group
has .misc as part of the name to allow further specialization if the users
wish it, such as .digital.tcp-ip.
The swap group is now rec.radio.swap. This recognizes a fact that became
evident shortly after the original group was formed: Hams don't just swap ham
radio gear, and other folks besides hams swap ham equipment. If you have radio
equipment, or test gear, or computer stuff that hams would be interested in,
here's the place. Equipment wanted postings belong here too. Discussions about
the equipment generally don't; if you wish to discuss a particular posting
with the buyer, email is a much better way to do it, and the other groups,
especially .equipment and .homebrew, are the place for public discussions.
There is now a regular posting with information on how to go about buying and
selling items in rec.radio.swap; please refer to it before you post there.
The first reorganization added two groups to the list, one of which is
rec.radio.amateur.policy. This group was created as a place for all the
discussions that seem to drag on interminably about the many rules,
regulations, legalities, and policies that surround amateur radio, both
existing and proposed. Recent changes to the Amateur Radio Rules (FCC
Part 97) have finally laid to rest the Great Usenet Pizza Autopatch Debate
as well as complaints about now-preempted local scanner laws hostile to
amateurs, but plenty of discussion about what a bunch of rotten no-goodniks
the local frequency coordinating body is, as well as the neverending no-code
debate, may still be found here.
The other added group is rec.radio.cb. This is the place for all discussion
about the Citizens' Band radio service. Such discussions have been very
inflammatory in rec.ham-radio in the past; please do not cross-post to both
rec.radio.cb and rec.radio.amateur.* unless the topic is genuinely of interest
to both hams and CBers - and very few topics are.
The rec.radio.info group is just what its name implies: it's the place where
informational messages from across rec.radio.* may be found, regardless of
where else they're posted. As of this writing, information posted to the group
includes Cary Oler's daily solar progagation bulletins, ARRL bulletins, the
Frequently Asked Questions files for the various groups, and radio
modification instructions. This group is moderated, so you cannot post to it
directly; if you try, even if your message is crossposted to one of the other
groups, your message will be mailed to the moderator, who is currently Mark
Salyzyn, VE6MGS. The email address for submissions to the group is
rec-radio-info@ve6mgs.ampr.ab.ca. Inquires and other administrivia should be
directed to rec-radio-request@ve6mgs.ampr.ab.ca. For more information about
rec.radio.info, consult the introduction and posting guidelines that are
regularly posted to that newsgroup.
The groups rec.radio.amateur.antenna, .equipment, .homebrew, and .space are
for more specialized areas of ham radio: discussions about antennas,
commercially-made equipment, homebrewing, and amateur radio space operations.
The .equipment group is not the place for buying or selling equipment; that's
what rec.radio.swap is for. Similarly, the .space group is specifically about
amateur radio in space, such as the OSCAR program and SAREX, the Shuttle
Amateur Radio EXperiment; other groups cover other aspects of satellites and
space. Homebrewing isn't about making your own alcoholic beverages at home
(that's rec.crafts.brewing), but rather construction of radio and electronic
equipment by the amateur experimenter.
Except for rec.radio.swap and rec.radio.cb, all of these newsgroups are
available by Internet electronic mail in digest format; send a mail message
containing "help" on a line by itself to listserv@ucsd.edu for instructions
on how to use the mail server.
All of the groups can be posted to by electronic mail, though, by using a
gateway at the University of Texas at Austin. To post a message this way,
change the name of the group you wish to post to by replacing all of the '.'s
with '-'s - for example, rec.radio.swap becomes rec-radio-swap - and send to
that name@cs.utexas.edu (rec-radio-swap@cs.utexas.edu, for example). You may
crosspost by including multiple addresses as Cc: entries (but see below). This
gateway's continued availability is at the pleasure of the admins at
UT-Austin, and is subject to going away at any time - and especially if
forgeries and other net.abuses become a problem. You have been warned.
A Few Words on Crossposting
===========================
Please do not crosspost messages to two or more groups unless there is genuine
interest in both groups in the topic being discussed, and when you do, please
include a header line of the form "Followup-To: group.name" in your article's
headers (before the first blank line). This will cause followups to your
article to go to the group listed in the Followup-To: line. If you wish
to have replies to go to you by email, rather than be posted, use the word
"poster" instead of the name of a group. Such a line appears in the headers
of this article.
One of the few examples of productive cross-posting is with the rec.radio.info
newsgroup. To provide a filtered presentation of information articles, while
still maintaining visibility in their home newsgroups, the moderator strongly
encourages cross-posting. All information articles should be submitted to the
rec.radio.info moderator so that he may simultaneously cross-post your
information to the appropriate newsgroups. Most newsreaders will only present
the article once, and network bandwidth is conserved since only one article is
propagated. If you make regular informational postings, and have made
arrangements with the moderator to post directly to the group, please
cross-post as appropriate.
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
"If my car ran OS/2, it'd be there by now" -- bumper sticker
GCS d++ p+ c++ l+ m+/- s/++ g++ w++ t+ r
--
73, Paul W. Schleck, KD3FU
pschleck@unomaha.edu
------------------------------
Date: 15 Mar 94 20:30:21 GMT
From: news-mail-gateway@ucsd.edu
Subject: Looking for information about Path Calculation
To: ham-digital@ucsd.edu
hello: Anybody know for books about propagation and path calculation=3F. I =
am working
with a packet radio network, and this information is important for a future=
expantion. Other
important information is antennas design. anybody a software for that=3F
Eduardo Millar C.
e-mail: emillar@enlces.ufro.cl
------------------------------
Date: 15 Mar 1994 15:31:34 -0800
From: ihnp4.ucsd.edu!news.cerf.net!ccnet.com!ccnet.com!not-for-mail@network.ucsd.edu
Subject: New GPS newsgroup
To: ham-digital@ucsd.edu
You might point your newsreader toward sci.geo.satellite-nav
Bob
--
Bob Wilkins work bwilkins@cave.org
Berkeley, California home rwilkins@ccnet.com
94701-0710 play n6fri@n6eeg.#nocal.usa.noam
------------------------------
Date: 15 Mar 1994 17:37:54 GMT
From: ihnp4.ucsd.edu!dog.ee.lbl.gov!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!gaia.ucs.orst.edu!frl.orst.edu!forrerj@network.ucsd.edu
Subject: W9GR port to TI DSK - UPDATE
To: ham-digital@ucsd.edu
Greetings,
Thanks to all that responded to the post of the W9GR code
on UCSD.EDU - looks like a lot of interest in DSP applications
for amateur radio.
I have updated the code, and fixed a few bugs - thanks to Tom, HB9JNX.
It made quite a difference, especially the performance of the denoiser.
Look for DSPDSK2.ZIP at UCSD.EDU /hamradio/packet/tcpip/packet/incoming
If you have the $99 TI DSK, also check out the new HF DSP modems
in TOR306.EXE at the same depository.
Enjoy.
Johan Forrer
KC7WW
------------------------------
End of Ham-Digital Digest V94 #71
******************************